From: Andrew Cooper Date: Sat, 12 Oct 2019 18:05:09 +0000 (+0100) Subject: docs: Extend with details about runtime microcode loading X-Git-Tag: archive/raspbian/4.14.0+80-gd101b417b7-1+rpi1^2~63^2~1286 X-Git-Url: https://dgit.raspbian.org/%22http:/www.example.com/cgi/%22https://%22%22/%22http:/www.example.com/cgi/%22https:/%22%22?a=commitdiff_plain;h=8dea47009f40511439ba2f59eafc5066ddea3124;p=xen.git docs: Extend with details about runtime microcode loading The xen-ucode utility is new with the late loading improvements in 4.13. Update the documentation suitably. Signed-off-by: Andrew Cooper Release-acked-by: Juergen Gross Acked-by: Jan Beulich --- diff --git a/docs/admin-guide/microcode-loading.rst b/docs/admin-guide/microcode-loading.rst index 1858ed4627..e27b641df3 100644 --- a/docs/admin-guide/microcode-loading.rst +++ b/docs/admin-guide/microcode-loading.rst @@ -101,3 +101,32 @@ which contains contains one of these two files:: The ``ucode=scan`` command line option will cause Xen to search through all modules to find any CPIO archives, and search the archive for the applicable file. Xen will stop searching at the first match. + + +Run time microcode loading +-------------------------- + +.. warning:: + + If at all possible, microcode updates should be done by firmware updates, + or at boot time. Not all microcode updates (or parts thereof) can be + applied at runtime. + +The ``xen-ucode`` utility can be used to initiate a runtime microcode load. +It will pass the blob to Xen, which will check to see whether the blob is +correct for the processor, and newer than the running microcode. + +If these checks pass, the entire system will be rendezvoused and an update +will be initiated on all CPUs in parallel. As with boot time loading, +diagnostics will be put out onto the console:: + + [root@host ~]# xl dmesg | grep microcode + (XEN) microcode: CPU0 updated from revision 0x1a to 0x25, date = 2018-04-02 + (XEN) microcode: CPU2 updated from revision 0x1a to 0x25, date = 2018-04-02 + (XEN) microcode: CPU4 updated from revision 0x1a to 0x25, date = 2018-04-02 + (XEN) microcode: CPU6 updated from revision 0x1a to 0x25, date = 2018-04-02 + (XEN) 4 cores are to update their microcode + (XEN) microcode: CPU0 updated from revision 0x25 to 0x27, date = 2019-02-26 + (XEN) microcode: CPU4 updated from revision 0x25 to 0x27, date = 2019-02-26 + (XEN) microcode: CPU2 updated from revision 0x25 to 0x27, date = 2019-02-26 + (XEN) microcode: CPU6 updated from revision 0x25 to 0x27, date = 2019-02-26